New MCP-native triage for Claude Code · Cursor · Windsurf →

Infrastructure, readable by humans
and agents.

Live server and domain metrics, audit findings, incident timelines, and remediation recipes — accessible to your team and to Claude Code, Cursor, and Windsurf via native MCP. One agent enrolls in seconds and catalogues every service, container, certificate, cron job and domain it finds — no asset registry, no YAML, nothing to declare. The fleet writes itself; you monitor, recover, and audit it from one fast console.

Free on your first host · Works with any provider · macOS, Linux, Web · Apache 2.0 agent
— Auto-discovery

Point at one server.
We find everything attached to it.

Most monitors stop at CPU · RAM · disk. We don't. The agent walks the host once and the rest of your fleet lights up — domains from web-server config, services from systemd, containers from Docker, certs, cron jobs, log paths — all monitored from the same install.

  • Domains from vhost config
  • Containers from Docker
  • Services from systemd
  • Certificates with expiry
  • Cron jobs from crontabs
  • Log paths per service
  • Network interfaces & routes
  • Service plugins (MySQL · PG · Redis · Nginx)
$ hostatlas add keywest.example.com
↓ AGENT SCAN · 1.4 s
Domains 14 found
Containers 8 running
Services 22 total
Certificates 14 monitored
Cron jobs 6 detected
Log paths 31 indexed
Zero config. No paths to declare. No agents per service.
— Product

Everything your fleet needs, nothing it doesn't.

Dense, honest, and fast. No dashboards pretending to be features. Every pixel on screen does work.

Unified fleet view

One table for every server across every provider. Health, cost, region, uptime — all one glance.

View servers →

Synced SSH client

Open a session on your laptop, close it on your phone. Multi-tab, split panes, key-synced, end-to-end encrypted.

Learn more →

Honest monitoring

CPU, memory, disk, network — sparklines where they belong, full charts when you need them. No upsell.

See metrics →

AI-assisted triage

Ask why keywest spiked at 14:32. Get a real answer with log excerpts, not a paragraph of filler.

Try AI →

Live network map

Visual fleet topology with real-time pulse. Click a node — SSH, metrics, logs, all right there.

Explore map →

Domains & SSL

Track 200 domains like 2. Renewals, DNS health, SSL expiry — with auto-renew and real Slack alerts that aren't noise.

Manage domains →
— What happens when you install the agent

From curl | bash to a catalogued fleet, in seconds.

Seven stations between the install command and the host being usable in your console — one per second, roughly.

  1. Install command sent to host
  2. Agent enrolled mTLS handshake
  3. Discovery scanning…
  4. Services 47 systemd units
  5. Containers 12 running
  6. Domains 23 + 8 certs
  7. Online in your fleet
$ curl -sSL install.hostatlas.app | sudo bash
→ enrolled · token ha_tk_3c91… · mTLS established
→ scanning systemd · /etc · docker · journalctl
● 47 systemd units · 5 failed · postgres, nginx, redis…
● 12 docker containers · nginx-edge, postgres-prod, redis-cache…
● 23 domains from nginx vhosts · 8 certs · 1 expiring in 12 d
✓ host online · first metrics arriving · ready to operate
db-prod-01 · assistant
you

postgres lock-wait p95 climbed 4× in the last hour on db-prod-01. why?

assistant

Two queries in pg_stat_statements account for 78 % of lock_wait_seconds in the last hour. Both run UPDATE orders SET … filtered by customer_id, which has no index.

Suggested fix
CREATE INDEX CONCURRENTLY orders_customer_id
   ON orders (customer_id);
ANALYZE orders;
dry-run via recipe open psql session
grounded in pg_stat_statements · query #41 slow log · line 4421 last 60 m of lock-wait metric
— AI where it helps

AI on tap, with receipts.

Every assistant answer cites the metric, log line or config it grounded on. No hand-wavy paragraphs. Suggestions arrive as runnable recipes you can dry-run, audit, and roll back — not as advice you have to translate into commands.

  • Database tuning Slow queries from pg_stat_statements / MySQL slow-log → suggested index, vacuum or config change. The query plan and the source rows are linked from the answer.
  • Service configs Nginx worker counts, PHP-FPM pool sizing, systemd-unit restart loops — surfaced from real telemetry, not a generic checklist.
  • Incident triage Many alerts grouped into one incident with a ranked root-cause hypothesis. Severity scored from downstream impact, not metric thresholds. AI Triage →
  • Anomaly detection Statistical baselines per metric per host. Holiday-aware, drift-aware. Catches the 30-second blip you would never have alerted on. Anomaly Detection →
  • Forensic replay Snapshot of fleet state at any past timestamp, ranked diff between two moments — for postmortems, audits, and "what changed before this broke." Coming soon

Read-only by default. Write actions need an explicit scope. Per-server toggle hides hosts from the AI gateway entirely — and the toggle itself stays web-auth-only.

— CLI-first

The CLI you'd build yourself, already built.

40+ commands covering the operator essentials — fleet status, server detail, service restart, recipes, logs, alerts, backups, attack mode, AI triage. Coloured tables, auto-width, ANSI-safe.

  • › Single binary · macOS · Linux · Windows · amd64 + arm64
  • › Restart services, run recipes, tail logs, manage backups, toggle attack mode
  • › Shell completion: bash · zsh · fish · powershell
  • › Bearer-token auth over TLS 1.3
~ — hostatlas — 80×24
$ hostatlas status
10 servers · 8 online · 1 degraded · 1 critical
47 containers · 24 domains · 3 alerts firing

$ hostatlas servers
HOST IP HEALTH OS AGENT
● yellowstone 192.0.2.18 12 / 100 Ubuntu 24 v1.0.72
◐ yosemite 198.51.100.42 71 / 100 Debian 12 v1.0.72
● denali 203.0.113.91 96 / 100 Ubuntu 24 v1.0.72
● sequoia 192.0.2.117 94 / 100 Debian 12 v1.0.72
● glacier 198.51.100.205 92 / 100 Ubuntu 24 v1.0.72

$ hostatlas restart nginx yosemite
→ restarting nginx on yosemite… ✓ active (running)

$ hostatlas ssh denali
→ opening HostAtlas SSH Client… ✓
$ _
— FAQ

Questions, answered honestly.

Do I need to install an agent?+

Yes, for the full feature set — discovery, auto-recovery, off-site backup, telemetry. Single binary, Apache 2.0, one-line install. Outbound-only; no inbound port required.

Does it work with my provider?+

Any Linux / FreeBSD / macOS host the agent can reach. First-party provider integrations today: Hetzner Cloud, DigitalOcean, Vultr, Linode, Cloudflare DNS, Hetzner Robot. AWS / GCP / Azure are on the roadmap; until then the agent works on those hosts, the cloud-side sync doesn't.

Where are my SSH keys stored?+

Encrypted in your OS keychain (macOS Keychain, Windows Credential Manager, libsecret). HostAtlas never reads them out except at connect time. SSH Gatekeeper additionally supports short-lived CA-signed certs so static keys aren’t required for gated access.

Is there a self-hosted version?+

Yes, on Enterprise — for air-gapped or sovereign deployments. The agent is always self-hosted; only the platform consumer side is a choice between our managed instance and your own.

How is this different from Datadog?+

Datadog watches. HostAtlas acts. We run auto-recovery before paging the human, attach pre-fire logs to incidents automatically, ship a CLI + MCP server that match the UI 1:1, sign the audit log. Pricing is per-host, not per-metric. The two coexist if you want them to.

What does it cost?+

Free tier covers a single host forever — no trial timer, no credit card. Starter covers 10 hosts, Pro 50, Enterprise unlimited. Off-site backup quota + AI features + retention scale with the tier. See pricing →

— Pick your starting point

Three ways into HostAtlas.

Same platform, different first ten minutes. Pick whichever sounds like a Tuesday you’ve had.

Your servers deserve better than a tab called “tools”.

Free tier on your first host, forever. No trial timer, no credit card. Install the agent and watch your fleet light up.

Get early access See all features